Problem Note 19565: Insufficient authorization to use C:\SAS\EMiner\Lev1\SASMain\sasgraph.wmf errors when running SAS Code node
When you use the SAS Code node in SAS® Enterprise Miner™ to generate SAS/GRAPH® software output, the node might fail with the following messages:
ERROR: Insufficient authorization to use
C:\SAS\EMiner\Lev1\
SASMain\sasgraph.wmf.
ERROR: Unable to open graphics device I/O.
ERROR: Unable to initialize graphics device.
ERROR: Driver SASGDWMF will not load.
where C:\SAS\EMiner is the name of your configuration directory.
The problem occurs when the default display output writes to the current active directory on the server. This is incorrect behavior for SAS Enterprise Miner. It should turn off the default graph display since graphics created in the node are written to GIF files in the node folder.
Use SAS Enterprise Miner Server Initialization code to circumvent the problem.
1. Create a file on the Workspace Server to use as an initialization file. This file acts as an "autoexec" file by passing SAS statements to the Workspace Server after the session initializes. The file should contain the statement:
2. Open SAS® Management Console and navigate to Application Management ->
Enterprise Miner -> Projects -> SASMain - Logical Workspace Server.
3. Open the Properties for the Workspace Server. Under the General tab,
set the value of Initialization Code to the file you created in step 1.
4. If you use more than one Workspace Server for SAS Enterprise Miner,
repeat steps 1 - 3 for each server.
Test your SAS Code node to be sure it now runs successfully. You should not
see a reference writing to a WMF file. You should see a reference writing to GIF files in the EMCODE/Graph folder.
Operating System and Release Information
SAS System | SAS Enterprise Miner | AIX | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft Windows XP Professional | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Standard Edition | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise Edition | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Datacenter Edition | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft Windows 2000 Professional | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft Windows 2000 Server | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft Windows 2000 Datacenter Server | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft Windows 2000 Advanced Server | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
64-bit Enabled Solaris | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Solaris | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Microsoft Windows NT Workstation | 5.1 | | 9.1 TS1M0 | |
z/OS | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Linux | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
HP-UX | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
HP-UX IPF | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
64-bit Enabled HP-UX | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
OpenVMS Alpha | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
64-bit Enabled AIX | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
Tru64 UNIX | 5.1 | 6.1 | 9.1 TS1M0 | 9.2 TS2M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Topic: | System Administration ==> Servers
|
Date Modified: | 2008-04-29 14:17:21 |
Date Created: | 2007-02-14 21:07:50 |